The boring phase of bug-fixing is still going, slowly but surely. Stable should be released next week, but with some people on vacation (Ben, Jitka, kovarex, Klonan, Sanqui) and with the release of WoW Classic, it might get slowed down a bit. (By the way, some of us will be playing on Pyrewood Village, Alliance, so if you want to have the chance of meeting Twinsen, kovarex or dominik while leveling, you can join that server). So since there's not much happening, this week we decided to explore some unpopular or controversial opinions about the game from within the team. In Wube we don't have a very strict management structure, everyone is free to have ideas and opinions about almost all aspects of the game. This means that with almost every change we argue and discuss a lot before making a final decision. Sometimes we argue about everything, from the smallest GUI change, to how a major feature should work. This is probably not a bad thing since this means changes are usually well thought out and unpopular ideas or changes don't make it to the game very often. Some people feel quite strongly about their opinions or sometimes the team is very divided on what should we do. Today we'll share some of those opinions and controversies. Keep in mind that these are simply opinions and none of them will actually make it into the game, we are simply sharing them to have an interesting discussion.
Hello there, I know a lot of you have been eagerly awaiting some solid information on the new planets, if so this blog is for you. Get comfy because it's a long one. As you already know, there are 4 new planets in the expansion. We will take an in-depth look at each planet's terrain, challenges, processes, technologies, and new gear, but not all at once. In some cases the planet content will be split into multiple parts. To kick things off I'll cover the terrain and natural aspects of the planet that is closest to being finished. I'll need to be in games master mode for this:
Hello, Today we are going to talk a little bit about a big feature in the expansion, Quality!
1.1 is getting close kovarex I have been tracking the amount of tasks and forum bugs required to finish 1.1 since the 1.0 release. This allowed me to get quantifiable feedback whether we are actually keeping the timeframe of the 1.1 release reasonable, or digging too deep and expanding the scope too much. If we extrapolate the graph, the 1.1 experimental should be ready next week.
Hello, It is time. STOMPY TIME! If you don't want spoilers on enemies and want to discover them naturally then you might want to skip this one. Let's continue the story from FFF-413. A trumpeting scream quietens all the small animals. You hear the breaking of waves followed by stomping: earth-shaking steps that are getting louder and louder. Looking in the direction of the sound, you see a cliff rising to a tall hill. The fungus at the top shakes a little with each stomp, but the source is somewhere further behind the hill. You ready your weapons, but the sound stops getting louder and instead moves to the right, then gradually fades into the distance. Whatever it was, it was big. After climbing the hill to investigate, you see a valley on the other side. Some large translucent green eggs float on a raft of slimy foam in a pool of shallow water. You get closer. The eggs are soft like jelly, the portion above water sagging under their own weight. In the centre is a dark blurry mass of... tangled limbs and eyes. This video has sound. Also available on YouTube in 4k. Suddenly the egg erupts and a clawed limb swipes at your face. A strange creature wriggles around in the water trying to claw at you, and through the splashing you make out 5 limbs like a starfish. A bulging head-like structure has many eyes on one side and a sponge-like material on the other. On the sides of its head are crests of transparent blisters that are inflating with air to form something like a paddle or wing. It drags itself around like some sort of ravenous tentacled baby. With the occasional lurching movement it launches itself at you, trying to grapple you with its limbs and bite you with its underside. The claws glance off your energy shield with minimal damage. Your personal laser defence springs into action and in a flash of light the newborn is cut to shreds. The laser then switches targets to the egg raft. A few moments later all the eggs burst into a horrifying swarm of angry thrashing creatures. The sea of flailing limbs and odd movement makes it difficult to target individuals. You bravely retreat back to the cliff and equip the flamethrower to protect yourself with a wall of fire. The undaunted wriggling creatures run straight into the fire and die soon after. Another trumpeting scream pierces the sky but this time it doesn't sound distant at all. A slender towering creature stares straight at you with its large bulging eyes. It strafes sideways circling you, gracefully stepping over cliffs and tree-like fungi with its 5 thin legs. It launches something from its head, a projectile high into the air and arcing toward you. You start retreating, but 4 wings spring from the sides of the projectile and it steers towards you like a homing missile. The flying creature rams into you, grappling you with its clawed limbs and slowing your movement. You throw it down to the ground and it becomes indistinguishable from the Wriggler you dispatched earlier. Your laser defences make short work of it, but without warning, you're struck by another projectile creature from the other side. Another Strafer has arrived and is also bombarding you. Both Strafers are staying out of range of your automated laser. You dash towards one of the Strafers with your submachine gun in hand, but as you do the Strafer to your front retreats and the other advances. They seem intent on keeping you at range, constantly circling while flinging homing projectiles. No matter, you have another weapon up your sleeve. You dash forwards again, this time with a rocket launcher in hand. A rocket snakes its way through the air and blasts its way into the first Strafer. The creature shrieks and attempts to retreat, but another rocket is already on its way. The second rocket strikes unerringly and a moment later, the Strafer is blown apart leaving a cloud of pieces to rain down on the swamp below. Stomp stomp stomp. The stomping has returned. A colossal spiked shell rises into view from behind a hill. It strides effortlessly over a cliff with its 5 huge armour-plated legs. This creature is clearly related to the others, but it is far heavier with a wide stance and thick legs. The central body or head region is like a shielding shell with small eyes peering through narrow holes. You fire some rockets at the Stomper and they do some damage, but nowhere near enough to take it down. You have very few rockets left and they won't be enough to kill the Stomper so it's better to save them for the other Strafer (which is difficult to catch otherwise). The Stomper charges towards you. Even with your exoskeleton equipment the Stomper can outrun you. You stand your ground with the submachine gun but you can't dodge effectively while you fire. As it gets close the tremors stress your shield, and thrown debris from its stomps pummel the shields further. The creature lands a foot directly on you and your shields falter. That hurt. This isn't working. You start moving again, not to outrun it but to outmanoeuvre it. It may be faster than you in a straight line, but it can't change directions as quickly. The other Strafer is still alive and flinging new enemies at you from a distance. By switching between dodging movement and bursts of SMG fire, you're able to evade most of the Stomper's damage and keep the number of Wrigglers low enough to not get overwhelmed. You wait for an opening when you're not being stomped on, swarmed, and the Strafer is in view. Away go the last 2 rockets and... success. The last Strafer falls dead. Now it's just you and the Stomper. A duel to the death. While continuing to dodge its feet, you make your way to a larger area of land to make your last stand. No more rockets. Gun ammo is low. Time for the flamethrower to shine. As you circle each other, you douse the arena in flames. The dance continues in flames until one of you falls. More fire, more spinning, more fire! The world becomes a hazy blur of flames, smoke, and death.
Hello, we finished with the regular Friday Facts series, and yet, there is still so much we want to talk about. I want to clarify, that we are not going to release FFF every week, but there are a few of them coming in the near future.
Hello, long time no see :) We obviously have a lot to talk about when it comes to the game changes we recently did, or plan to do, but we don't want to share any of it yet. Yet, there is currently a topic very relevant to us and we can share it without revealing any specific changes to the game. Today's post will be quite technical and related to programming, so if you just came for the game news, you can safely skip this one.
GUI progress update (kovarex) This is a continuation of the last status report from FFF-269. As it might not be a surprise, the biggest bottleneck of the 0.17 release is the GUI. I like to believe, that we have learned a lot from the pitfalls of the collaborative creative process of GUI. This is the typical way we were redesigning the GUI: Two to three people started discussing what could be cool to change in the particular GUI. Some people randomly joined and left the ongoing discussion. Arguments to discard certain ideas have to be repeated over and over. Then the discussion is ended because of something. A week later people start talking again, most of them forgot most of the stuff, or were discussing it with different people, so they assume some details of the changes to be understood by everyone, while they aren't. They come to an agreement how it should be done. They have a random discussion about it a week later and figure out, they had completely different ideas about how it should be done, they just didn't articulate them precisely. Both are kind of angry to have to reopen and re-negotiate the subject again. Someone starts to implement the GUI, but half-way through it is uncovered, that there was another layer of misunderstanding when specifying how should the work be done, and we need to go to step 1 again and repeat. Since many GUIs are thought and worked on in parallel, these situations overlapped and amplified the problems of mixing things up in our heads about what we agreed on in which GUI. Luckily, we eventually figured out, that it can't be done like this, and since there is a lot of work in the GUI, we need to make a process. It goes like this: First, there is some general discussion about the GUI, all team members can share their ideas. kovarex + Twinsen sit alone in the office, and discuss for some time (can be hours), all the pros and cons of how things should be done, and make some agreement. Twinsen writes a detailed UX document about the GUI containing the structure, and more importantly the behaviour, in a detailed manner. Twinsen + kovarex discuss the UX document and propose changes until they agree on the final version. Albert + Aleš take the UX document and create a UI mockup based on it. kovarex + Twinsen + Albert agree on the UI mockup or propose changes. Someone is assigned to implement the GUI based on the UX document and UI mockup kovarex reviews that the implementation is correct and points out some inconsistencies that he can see. Part of this step is making sure, that we share as many GUI styles and code as possible across different GUIs. kovarex + Albert have a final look on the implementation and fix final details until they both agree that the screen is fully finished. Having the UX documents/UI mockups always available proved to be a huge time saver. Not only it helps us to solve the communication problems, we also don't have to remember and re-articulate decisions from some time ago as we can just open the document and see what we agreed on and instantly continue where we left off. A good part of this strict pipeline is that we now have better knowledge of the state of the work progress. These are the GUI screens that we hope to deliver for 0.17: .header_cell { text-align:center; font-weight: bold; } .finished { text-align:center; font-weight: bold; } .not_finished { text-align:center; font-weight: bold; } .finished_gui_table { border-spacing: 10px; } .finished_gui_table td { border: 1px; border-style:solid; padding: 5px; } General UX UX draft UX review UI mockup UI review Implementation draft Implementation review Final review Load map Save map Graphics settings Control settings Sound settings Interface settings Other settings Map generator Technology GUI Technology tooltip Recipe/item/entity tooltip Action bar Shortcut bar Train GUI Manage/Install mods Main screen chat Recipe explorer Character screen Menu structure New game Help overlay Chat icon selector Blueprint library You can see, that there is still a lot of to do, but the work tends to accelerate as more and more of the GUI layouts/tilesets/standards are being finalized and reused. The conclusion is that 0.17 experimental in January is possible, but it might be February as well :).
